home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Columbia Kermit
/
kermit.zip
/
newsgroups
/
misc.19950329-19950528
/
000282_news@columbia.edu_Sun Apr 30 08:59:23 1995.msg
< prev
next >
Wrap
Internet Message Format
|
2020-01-01
|
2KB
Received: from apakabar.cc.columbia.edu by watsun.cc.columbia.edu with SMTP id AA16575
(5.65c+CU/IDA-1.4.4/HLK for <kermit.misc@watsun.cc.columbia.edu>); Sun, 30 Apr 1995 17:04:13 -0400
Received: by apakabar.cc.columbia.edu id AA17538
(5.65c+CU/IDA-1.4.4/HLK for kermit.misc@watsun); Sun, 30 Apr 1995 17:04:12 -0400
Path: news.columbia.edu!panix!news.mathworks.com!gatech!swrinde!cs.utexas.edu!news.cs.utah.edu!cc.usu.edu!jrd
From: jrd@cc.usu.edu (Joe Doupnik)
Newsgroups: comp.protocols.kermit.misc
Subject: Re: MS-Kermit 3.14 PL 3 crash
Message-Id: <1995Apr30.145923.49249@cc.usu.edu>
Date: 30 Apr 95 14:59:23 MDT
References: <3o0aub$ipr@senator-bedfellow.MIT.EDU>
Distribution: world
Organization: Utah State University
Lines: 24
Apparently-To: kermit.misc@watsun.cc.columbia.edu
In article <3o0aub$ipr@senator-bedfellow.MIT.EDU>, davis@space.mit.edu writes:
> Hi,
>
> It seems that MS-Kermit 3.14 Patch Level 3 will crash upon startup if
> there is less than 270K free memory. Has this been noticed before? I would
> rather have it abort with an insufficient memory error.
>
> One way to verify this is to run Kermit, push to DOS, then using MEM to
> monitor free memory, keep spawning new command.coms until the memory drops
> below about 270K. Then run a new kermit.
>
> The system is a 486 DX2 running DOS 6.22 with no TSRs loaded.
------------
MSK does complain if not enough memory is available to complete
the startup process. I think the situation maybe that DOS itself is locking
up during the attempted load. The reason I suggest this is I tried the
experiment twice, once with full networking going and again without. The
full networking case yielded a dead machine, interrupts off, no keyboard
lights, etc. Kermit itself does not do such things, and that leaves DOS.
The second experiment was before networking and Kermit #2 complained about
insufficient memory and refused to load; all was well otherwise. This too
suggests that in the first experiment Kermit.exe itself did not get fully
loaded and did not have a chance to execute any instructions.
Joe D.